Fixes #26318

Testing done

• Added a regression test createLogRecorderWithNonAsciiName in LogRecorderManagerTest.
• The test creates a log recorder named Journal d’accès and verifies that the configure URL resolves with an encoded path segment.
• CI builds are running for full validation.

Screenshots (UI changes only)

Before

N/A (no UI layout change)

After

N/A (no UI layout change)

Proposed changelog entries

• Redirect to the correct URL when creating log recorders with non-ASCII names.

Proposed changelog category

/label bug

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate. (No new public API in this PR.)
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable. (No new deprecations in this PR.)
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, new or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation). (No JS/UI behavior change in this PR.)
• For dependency updates, there are links to external changelogs and, if possible, full differentials. (No dependency updates in this PR.)
• For new APIs and extension points, there is a link to at least one consumer. (No new API/extension point in this PR.)

Desired reviewers

@jenkinsci/core-pr-reviewers

Before the changes are marked as ready-for-merge:

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, be a Bug or Improvement, and either the issue or pull request must be labeled as lts-candidate to be considered.